Skip to content

feat(guard): place governing rule text adjacent to the action it governs (#241) - #249

Merged
CryptoJones merged 1 commit into
mainfrom
feat/241-rule-action-adjacency
Aug 14, 2026
Merged

feat(guard): place governing rule text adjacent to the action it governs (#241)#249
CryptoJones merged 1 commit into
mainfrom
feat/241-rule-action-adjacency

Conversation

@CryptoJones

Copy link
Copy Markdown
Owner

Implements #241: governing excerpt inside the repo-work deny (demand first, 1,600-char cap, fail-open on missing note); full re-injection on action-shaped turns via a fixed pattern list; preflight top-1 → top-2 with the second note strictly title+summary and skipped on economy. Tests cover all three plus the missing-note fallback. 950 passed; ruff clean. Version 8.4.0.

Closes #241

🤖 Generated with Claude Code

…rns (#241)

Repo-work denies embed the git-rules note's summary + leading excerpt
(capped) after the demand sentence; action-shaped turns re-inject the
full preflight excerpt instead of the summary-only downgrade; preflight
surfaces a runner-up match as title+summary (skipped on economy).

Closes #241

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Comment thread src/omind/guard.py
message (#241). Best-effort: any failure returns ``""`` — the deny still
stands on its demand sentence alone."""
try:
from omind import recall
Comment thread src/omind/guard.py
if len(titles) < 2:
return ""
try:
from omind import ai_usage, recall
@coderabbitai

coderabbitai Bot commented Aug 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@CryptoJones, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 21 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a25d814e-c5ec-4510-9426-b186dcb0a2d5

📥 Commits

Reviewing files that changed from the base of the PR and between 2e25388 and d4d8efb.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (5)
  • CHANGELOG.md
  • pyproject.toml
  • src/omind/__init__.py
  • src/omind/guard.py
  • tests/test_guard.py

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@CryptoJones
CryptoJones merged commit 0fb1808 into main Aug 14, 2026
16 checks passed
@CryptoJones
CryptoJones deleted the feat/241-rule-action-adjacency branch August 14, 2026 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(guard): place governing rule text adjacent to the action it governs

2 participants